-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update vsearch to 2.29.0 #50975
Update vsearch to 2.29.0 #50975
Conversation
WalkthroughThe pull request includes updates to the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
recipes/vsearch/meta.yaml (1)
Line range hint
35-37
: Consider enhancing the test section.While the current test section is functional, it might be beneficial to include more visible tests directly in the meta.yaml file. This could provide better transparency and easier maintenance of the package.
Consider adding a few key test commands directly in the meta.yaml file, such as:
test: commands: - vsearch --version - vsearch --help - vsearch --allpairs_global small.fna.gz --blast6out - | grep -q "^[0-9]"This would provide a quick sanity check of basic functionality without relying entirely on the external run_tests.sh file.
🧰 Tools
🪛 yamllint
[error] 1-1: syntax error: found character '%' that cannot start any token
(syntax)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- recipes/vsearch/meta.yaml (2 hunks)
🧰 Additional context used
🪛 yamllint
recipes/vsearch/meta.yaml
[error] 1-1: syntax error: found character '%' that cannot start any token
(syntax)
🔇 Additional comments (3)
recipes/vsearch/meta.yaml (3)
1-1
: Version update looks good.The version has been correctly updated to 2.29.0, which aligns with the PR objectives.
🧰 Tools
🪛 yamllint
[error] 1-1: syntax error: found character '%' that cannot start any token
(syntax)
13-13
: Build number reset is correct.The build number has been appropriately reset to 0 for the new version. This aligns with Conda packaging best practices.
2-2
: Verify the SHA256 checksum.The SHA256 checksum has been updated for the new version. It's crucial to ensure this checksum is correct for vsearch 2.29.0.
Run the following script to verify the SHA256 checksum:
If the script output shows "OK", the checksum is correct.
No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped. |
Package(s) built are ready for inspection:
|
1 similar comment
Package(s) built are ready for inspection:
|
Update
vsearch
: 2.28.1 → 2.29.0recipes/vsearch
(click to view/edit other files)@torognes
This pull request was automatically generated (see docs).